-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Upgrade to apkeep 0.16.0, python 3.11 & Debian bookworm #612
Conversation
Just a heads up on something: is it possible to use/try several devices in case this would be needed? I don't think it would apply to many applications, but maybe some would not allow a device that's too recent? |
Tell me if you want I update the documentation to get the token the first time :) |
@Jean-BaptisteC I think it could be a good idea for the documentation if you can, yes |
@Jean-BaptisteC Let's add a link to https://github.com/EFForg/apkeep/blob/master/USAGE-google-play.md in order to not duplicate the information :) |
Just tested locally and I could make it work, I'll push my changes into this branch @Jean-BaptisteC |
Why device has been removed? |
The default device is Specifying |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code reviewed and tested with Docker.
Work like a charm! I can also confirm that applications we could not download before are now downloadable.
Thanks everyone.
Converted to draft so we don't merge it before our production is upgraded to Debian 12 soon! |
Fixes #611
Did we need to send a first request to get an aas_token, maybe it can be done manually the first time?
To reduce failed downloads, I use Pixel 7 device to download APK.
Needs help to test :)
Edit : Fixes #598 too